Skip to content

get_l1_object: only set L0 and L1 if they are non-empty #4923

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

smowton
Copy link
Contributor

@smowton smowton commented Jul 17, 2019

This is important because an expression "L0: '', L1: ''" is semantically equivalent to
one with either index not specified at all, but they do not compare equal (irept::compare
distinguishes an empty-string from an absent key), leading to confusing behaviour when
ssa_exprts are used as keys in a map, for example.

@smowton smowton force-pushed the smowton/fix/get-l1-object-empty-strings branch from 72d4a33 to be843a8 Compare July 17, 2019 17:08
This is important because an expression "L0: '', L1: ''" is semantically equivalent to
one with either index not specified at all, but they do not compare equal (irept::compare
distinguishes an empty-string from an absent key), leading to confusing behaviour when
ssa_exprts are used as keys in a map, for example.
@smowton smowton force-pushed the smowton/fix/get-l1-object-empty-strings branch from be843a8 to 56bb4c4 Compare July 23, 2019 17:08
Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✔️
Passed Diffblue compatibility checks (cbmc commit: 56bb4c4).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/120260619

@smowton smowton merged commit 3ad2a27 into diffblue:develop Jul 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants